5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
- Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-17: Using Event Points

Post PCF Update


The Post PCF Update event point is triggered by a change to a record. As a result, its execution is dependent upon the existence of a PCF. If the PCF is not stored, APPX still senses the change and executes the event point.

Post PCF Update is found exclusively in input processes, and executes only in the data addition, data modification, and data deletion interactive phases. It executes immediately after the PCF record is saved.

Post PCF Update is generally used to perform manipulation of records in files other than the PCF. Remember that Pre-PCF Update is used to perform actions on the PCF when the operating system has a hold on the PCF record. By the time APPX executes Post PCF Update, the system has saved and relinquished control of the PCF record. If you wish to manipulate a PCF record in this event point, you must reread and hold it.

Because the event point only executes when a PCF record has just been saved, you can use this event point to perform actions on non-PCF records that depend upon the PCF record you saved. Examples include resetting a journal printed flag to N whenever a user changes transaction information related to the journal, and updating a committed quantity field that is in an inventory application that is based upon changes to a sales order in an order entry application.

Application Design Manual                                         "Powered by Appx Software"

473

©2006 By APPX Software, Inc. All Rights Reserved